Systems and methods for providing user preferences for a connected device

ABSTRACT

An information wallet system includes an information wallet account associated with a user of the system, and a server having a memory and a processor. The processor is configured to receive user information from a user computing device, wherein the user information is related to a user of the information wallet account, determine, based on the user information, one or more user settings preferences related to a second computing device, receive an information request, wherein the information request includes a request to send the one or more user settings preferences to the second computing device, and to send the one or more user settings preferences to the second computing device, wherein the one or more user settings preferences are useable by the second computing device to adjust one or more settings of the second computing device.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 14/195,182, filed on Mar. 3, 2014 and titled “SYSTEMS ANDMETHODS FOR PROVIDING USER PREFERENCES FOR A CONNECTED DEVICE,” whichclaims priority to U.S. Provisional Patent Application No. 61/806,686,filed on Mar. 29, 2013 and titled “Systems and Methods for InformationStorage and Communication,” and U.S. Provisional Patent Application No.61/922,486, filed on Dec. 31, 2013 and titled “Systems and Methods forProviding User Preferences for a Connected Device,” all of which areincorporated by reference in their entireties and for all purposes.

BACKGROUND OF THE INVENTION

A device often includes settings for tailoring the device to a specificuser. For instance, a vehicle includes many settings, such as seatposition, radio presets, satellite radio subscription information,mirror positions, Bluetooth pairing settings, desired temperature,favorite navigation destinations, and the like in order to providegreater comfort for a user (e.g., driver) of the vehicle. The user mayadjust the settings of the vehicle to fit the particular characteristicsof the user. However, when a user enters a rental car, for instance, theuser's desired settings will not be pre-programmed into the car. Theuser is required to adjust each individual component of the vehiclehaving adjustable settings to achieve a comfort similar to that providedby the user's vehicle. Individuals may be required to take similar stepswhen using any device having adjustable settings and being available foruse by more than one user, or when purchasing any new device havingadjustable settings. Enhanced systems and methods of facilitating suchadjustments and storing such information are provided.

SUMMARY OF THE INVENTION

An embodiment of the present disclosure relates to an information walletcomputing system. The system includes an information wallet accountassociated with a user of the system, and a server having a memory and aprocessor. The processor is configured to receive user information froma user computing device, wherein the user information is related to auser of the information wallet account, determine, based on the userinformation, one or more user settings preferences related to a secondcomputing device, receive an information request, wherein theinformation request includes a request to send the one or more usersettings preferences to the second computing device, and to send the oneor more user settings preferences to the second computing device,wherein the one or more user settings preferences are useable by thesecond computing device to adjust one or more settings of the secondcomputing device.

Another embodiment of the present disclosure relates to a method forpairing an information wallet account with a second computing device,the method being implemented by a server residing in a financialinstitution computing system and having a memory and a processor. Themethod includes receiving user information from a user computing device,wherein the user information is related to a user of the informationwallet account, determining, based on the user information, one or moreuser settings preferences, wherein the user settings preferences arerelated to the second computing device, receiving an informationrequest, wherein the information request includes a request to send theone or more user settings preferences to the second computing device,sending the one or more user settings preferences to the secondcomputing device, wherein the one or more user settings preferences areuseable by the second computing device to adjust one or more settings ofthe second computing device, receiving additional user information fromthe second computing device, wherein the additional user information isrelated to use of the second computing device by the user, and updatingthe one or more user settings preferences based on the additional userinformation.

Another embodiment of the present disclosure relates to a method forproviding information from an information wallet account to a secondcomputing device, the method being implemented by a server residing in afinancial institution computing system and having a memory and aprocessor. The method includes receiving user information from a usercomputing device, wherein the user information includes one or more usersettings preferences related to the second computing device andassociated with a user of the information wallet account, receiving aninformation request, wherein the information request includes a requestto send the one or more user settings preferences to the secondcomputing device, and sending the one or more user settings preferencesto the second computing device, wherein the one or more user settingspreferences are useable by the second computing device to adjust one ormore settings of the second computing device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a computer-implemented informationwallet system according to an exemplary embodiment.

FIG. 2 is a schematic diagram of a computer-implemented informationreceiving system of the information wallet system in FIG. 1 .

FIG. 3 is a schematic diagram of a computer-implemented informationsharing system of the information wallet system of FIG. 1 .

FIG. 4 is a schematic diagram of a computer-implemented informationprocessing system from FIG. 1 .

FIG. 5 is a diagram showing information synchronization between variousadapters and user applications.

FIG. 6 is a schematic diagram of another computer-implementedinformation wallet system according to an exemplary embodiment.

FIG. 7 is a flow chart diagram showing a process for providing usersettings preferences for a paired computing device.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The systems and methods, described in greater detail below, provide aninformation wallet system configured to receive information from a userand enable the user to communicate the information in a highly secure,convenient, efficient, time-saving, and cost-effective manner. Thesystems and methods may allow merchants and other businesses to reducetheir reliance on technologies such as card swipe, card readers, cashmachines, custom kiosks, cash registers, specialized scanners, etc. Theinformation may be stored in the cloud and/or locally on the customer'sdevice. The information may be stored in a financial institutioncomputing system, exclusively or non-exclusively, and maintained by thefinancial institution. The information may be accessible to theindividual and other entities, with the approval of the user, using amobile device (e.g., laptop, mobile phone, tablet, etc.) or othercomputer devices. The systems and methods may allow a user to store usersettings preferences for a device and automatically send the preferencesto the device to update the settings. The user may be able to update theuser settings preferences using an information wallet application storedon a user device.

Referring to FIG. 1 , a computer-implemented information wallet system100 is shown that may be used by a customer (also referred throughout asa user) to set up and utilize an information wallet account using a usercomputing device 120 (i.e. laptop, mobile phone, tablet, or homecomputer). In the various embodiments, data storage and otherfunctionality for the information wallet system 100 may include acloud-based storage computing system 150 and/or other functionalityprovided by the information wallet computing system 115. The informationwallet computing system 115, in one example embodiment, may be provideda financial institution computing system (e.g., a bank computingsystem). The user may be an individual consumer that may have one ormore accounts with the financial institution and has also established aninformation wallet account with the financial institution. In anotherembodiment, the user may not have a financial account with the financialinstitution but may nevertheless have established an information walletaccount with the financial institution. The information wallet system100 is configured to meet the varied needs of users in the embodimentsabove and embodiments discussed below. In other embodiments, theinformation wallet system 100 may be provided by other entity computingsystems 105. Other entity computing systems may comprise a secondfinancial institution, a merchant, a health care organization, agovernment organization, an employer, a customer, or other entity with acomputing system. The other entity computing systems 105 may store datathat is accessed by the information wallet system 100 (e.g., in externalentity storage systems 160 as shown in FIGS. 2, 3, and 5 ). Theinformation wallet system 100 may include a link out to the data storedin the other entity computing systems 105 such that the data stored bythe other entity computing systems 105 is seamlessly accessed by theinformation wallet computing systems 115. The information walletcomputing system 115 may be used to facilitate storing information andcommunicating stored information to one or more entities, potentiallyvia a user computing device 120.

Referring to FIG. 1 , information wallet system 100 may include, amongother systems, entity computing systems 105 (i.e. a merchant computingsystem and/or a financial institution computing system), an informationwallet computing systems 115, a user computing device 120 (which mayinclude a laptop, home computer, mobile phone, tablet, or any othercomputing devices), and cloud storage computing systems 150. Thecomputing systems and devices 105, 115, 120, and 150 may communicatethrough a cloud network, which may include one or more of the Internet,cellular network, near field communication (NFC), Bluetooth connection,Wi-Fi, Wi-Max, a proprietary banking network, etc. The entity computingsystems 105, information wallet computing systems 115, user computingdevices 120, and cloud storage computing systems 150 may each comprise acomputer system (e.g., comprising one or more processors) configured toexecute instructions, send and receive data stored in non-transitorymemory, and perform other operations to implement the operations andfunctions described herein associated with logic or processes as shownin the figures and discussed throughout the disclosure.

The entity computing systems 105 are implemented by entities thatinteract to exchange information with users. Such entities, as describedabove, may include a financial institution, a merchant of goods orservices, a health care organization, a government organization, anemployer, a customer, or any other entity or combination of entities.The entity computing system 105 may, for example, be provided by anyentity that provides goods or services to consumers. The entities mayenter into transactions with the user and/or may exchange informationwith the user. For example, the entity computing systems 105 mayimplement an Internet destination (e.g., website) where users may obtainuser names/login IDs or otherwise become registered members.Registration of the users as members could allow a user and entity toconnect quickly and securely, determine and share a variety of relevantinformation, and optimize the shared information to meet both the userand entity needs. As another example, the entity computing systems 105may be provided at a bricks and mortar location where the user receivesgoods or services, such as a store, a hospital, a restaurant, a hotel,etc. The information exchanged may, for example, relate to the goods orservices received by the user at the location.

The user computing devices 120 may be used by a user to create aninformation wallet account and interact with an entity computing system105. The user computing devices 120 may include mobile devices such as asmart phone, portable gaming device, portable music listening device,portable digital or electronic viewing device, or another suitablewireless device. The user computing device 120 may comprise networkinterface logic, a display device, an input device, and an informationwallet application 140. Network interface logic may include, forexample, program logic that connects the user computing device 120 tothe network. As described in greater detail below, for example, the usercomputing device 120 may display screens to prompt the user to reviewand/or approve data transfer requests, to request data from the user,etc. Such screens may also be used to prompt the user to specifyparameters regarding the level of security to be associated withdifferent elements of data regarding the user. For example, datarequests including a mailing or physical address may be assigned ahigher level of security than data requests involving an email address.Such screens are presented to the user via the display device. Thedisplay device may be interactive, for example touchscreen. An inputdevice may be used to permit the user to initiate access to theinformation wallet and to facilitate sending/receiving requestedinformation to/from the entities. In one embodiment, the input devicemay allow a user to access and redeem a gift stored in the informationwallet system 100.

FIG. 1 shows information wallet computing system 115 disposed betweenthe entity computing systems 105 and the user computing devices 120. Inone embodiment, the information wallet computing system 115 is resideswithin a financial institution computing system. The information walletcomputing system 115 may comprise program logic executable by andbetween the entity computing systems 105 and the user computing devices120 to implement at least some of the functions described herein. Aswill be appreciated, the level of functionality that resides on theentity computing systems 105 or information wallet computing system 115,as opposed to the user computing devices 120, may vary depending on theimplementation. The information wallet computing system 115 may includemodules such as a business client system, business mobile system, andcustomer system. The business client system module may provide thebackend support of the information wallet application disposed on abusiness client side. Likewise, the business mobile system and customersystem modules may provide backend support of the information walletapplication disposed on a business mobile device or a customer device.The information wallet computing system 115 may also host the cloudstorage computing system 150.

The information wallet computing system 115 may allow the user computingdevices 120 to interact with entity computing systems 105. In oneembodiment, the information wallet computing system 115 facilitates theexchange of information between the user computing device 120 and theentity computing system 105. For example, the information walletcomputing system 115 may receive information from a user computingdevice 120 and transfer that information to the entity computing system105. In one embodiment, the information received from the user computingdevice 120 corresponds with a request to the information walletcomputing system 115 to retrieve certain information. The informationwallet computing system 115 may receive the request, access the cloudstorage computing system 150, retrieve the requested information, andforward the information as requested to the entity computing system 105.In another embodiment, the same process may apply for transferringinformation from an entity computing system 105 to the user. Theinformation wallet computing system 115 may receive information from anentity computing system 105 and transfer that information to a usercomputing device 120. The information received may correspond with arequest to the information wallet computing system 115 to retrievecertain information from the cloud storage computing system 150. Theinformation wallet computing system 115 may receive the informationincluding the request from the entity computing system 105, access thecloud storage computing system 150, retrieve the requested information,and transfer the information to the user computing device 120. Forembodiments described throughout the disclosure, any user, customer, orentity may create an information wallet account through the informationwallet system 100 using an available computing device.

The cloud storage computing system 150 may store information that isprovided by the user, e.g., after the information wallet is enriched byone or more of the processes shown in FIG. 2 , described below. Thecloud storage computing system 150 may encrypt the data regarding theuser. In some embodiments, the cloud storage computing system 150 maypermit an entity to access the data based on a permission or securitylevel granted by a user. For example, if a user configures aninformation wallet account to allow broad permission for sharinginformation about vehicles owned by the user, then an entity seeking theuser's vehicle information may obtain that information without waitingfor further approval. The entity may solicit the information from thecloud storage computing system 150 through the information walletcomputing system 115, and the information wallet computing system 115may retrieve the information based on pre-set permission by the user.The cloud storage computing system 150 may give the user full control ofthe information stored by the user in the cloud storage computing system150. The system is configured such that an outside computing system mayonly access information in conformance with permission and securitylevels set by a user.

Some of the user information may be stored in the external entitystorage systems 160 of entities 105. Accordingly, some data may bestored outside of the cloud storage computing system 150 and the usercomputing devices 120. In these situations, the information walletcomputing system 115 may include a link out to the data stored in theexternal entity storage systems 160. The link out may be a token that isstored in the cloud storage computing system 150 or in the informationwallet application 140 running on the user computing devices 120. Thelink out indicates to the information wallet system 100 the location andcontent of the information stored the external entity storage systems160 of entities 105 such that the data can be integrated into the user'sinformation wallet without having to store the data in the informationwallet computing system 115. For example, a user may opt not to storemedical information (e.g., an MM, X-rays, etc.) in the informationwallet computing system 115, but rather in a records database of theuser's medical provider. In this situation, the information walletcomputing system 115 may be configured with a link out to the medicalinformation stored in the records database of the medical provider suchthat that the information wallet system 100 has access to the externallystored data.

In an example embodiment, the information wallet system 100 allowsinteroperability between various entity computing systems 105 (e.g.,external entity storage systems 160), information wallet computingsystems 115, user computing devices 120, and other relevant systems. Inorder to provide the interoperability with each of the above listedsystems, various adapters may be utilized on a plurality of systems.Adapters facilitate integrating computing systems of differenttechnological platforms in a manner that allows different computingsystems to connect with the information wallet system 100. The adaptersmay be implemented, for example, using plug-ins or Application ProgramInterfaces (“APIs”), which comprise a set of software components thatadd specific abilities to a larger software application. The plug-ins orAPIs, in one embodiment, adapt the pre-existing enterprise computingsystem to connect with the information wallet system 100. The plug-insor APIs may also enable the functionality of an application to becustomized, such as an enterprise application that supports businessoperations of a business entity or an application (e.g., browser)executed on a user computing device 120. The application may becustomized to meet any need or requirement of any particular entity,business, or customer using the information wallet system 100. Forexample, a hotel may have enterprise software with a plug-in installedthat displays a button screen (i.e., “Request via Info Wallet”) in thecheck-in screen. Upon the engaging the button, such as by pressing thebutton, the enterprise software may execute the plug-in. The plug-inmay, for example, initiate the generation of a Bluetooth signal toestablish Bluetooth contact with a user computing device 120. A randomPIN may be verbally or textually communicated to the user for entry intothe user computing device 120 in order to initiate Bluetooth pairingwith the user computing device 120 of the user. The plug-in maytherefore, via Bluetooth, request information from the informationwallet system 100 of the user that is checking into the hotel. In otherscenarios, the connection may be made by way of another type of wirelessconnection, such as but not limited to, Wi-Fi, WAN, 3G, 4G, NFC, etc.The plug-ins or other adapters may use a request/response protocol tocommunicate messages and execute code. The plug-ins or APIs may sendmessages in a predetermined format that contain a list of data that isrequested. The user computing device 120 may receive the Bluetoothrequest and generate a screen requesting permission to send therequested information. The adapters may also request certain packages ofdata. For example, if a common adapter is developed that is used byvarious hotels using the same enterprise software, then all hotels mayask for the same package of data, and that information may bestandardized and prepackaged to be sent each hotel. As will beappreciated, similar arrangements may be implemented in other contexts(e.g., healthcare providers, merchants, etc.).

The cloud storage computing system 150 may cooperate with theinformation wallet computing system 115 on the user computing device 120to provide different levels of security to the information stored in thecloud storage computing system 150. For example, the user may configurethe information wallet to provide the address and phone number of theuser with a first (relatively low) level of security, to provide acredit card number of the user with a second (higher) level of security,to provide the credit card cvv value with a third (still higher) levelof security, and to provide the user's social security with a fourth(even higher) level of security. As will be appreciated, any number ofdifferent levels of security may be provided. The level of securitygiven to any particular data element may be determined as a matter ofdefault (e.g., information wallet configuration may by default dictatethat the user's social security number is given a higher level ofsecurity than the user's phone number), based on user-specified inputs(e.g., the user may be given the ability to set security on a dataelement by data element basis, to set security for groups of relateddata (e.g. health data vs. financial data), and/or to set security inanother manner), etc. The level of security assigned to a specific typeof information or data may alter the steps that must be taken in orderfor the information wallet system to relinquish the information to anoutside computing system. For example, information and data with arelatively low level of security may be pre-approved for sharing by theuser, and the information wallet computing system 115 may relinquish theinformation upon request by the entity. On the other hand, informationor data assigned a higher level of security may require the informationwallet computing system 115 to contact the user through the usercomputing device 120 and solicit authorization from the user. Theauthorization may be supplied by a number of ways, including, forexample, an electronic signature, a pin number, a finger print, ordirect user authorization through the user computing device 120.Security and/or validity of an information request is not exclusively“fixed.” The informational wallet will have the capability to determinewhether the “context of the transaction” is valid. Accordingly, ifcertain known patterns of fraud or trolling for information are detectedthe user may be alerted to the potential fraud or troll for data.Analytical models may be used to determine the probability of a valid orinvalid data request.

As will also be appreciated, the security precautions taken in thecontext of a particular transaction may be determined not only based onthe level of security associated with a particular information or dataelement, but also based on other factors, such as the identity of theentity requesting the information. For example, the user may configurethe information wallet such that the user's spouse is granted access toall of the user's data, regardless of the level of security with whichthe data is associated. As another example, the information wallet maybe configured such that the user's health care providers are giveneasier access to the user's health-related data, and the user'saccountant is given easier access to the user's financial data. Hence,the user's approval may be prompted prior to the user's financial databeing provided to the user's health care provider, but not prior to theuser's financial data being provided to the user's accountant.Conversely, the user's approval may be prompted prior to the user'shealth-related data being provided to the user's accountant, but notprior to the user's health-related data being provided to the user'shealth care provider. As will be appreciated, the level of securityprovided may also be dependent on other factors, such as the time of daythat the data is being requested (e.g., a request for data occurring inthe middle of the night might be considered to be more likely to befraudulent in some circumstances), the location of the requester (e.g.,the IP address of the requester may indicate that the requester isoverseas), the location of the user (e.g., the GPS signals from the usercomputing device 120 may indicate that the user is at a location thatwould not normally be associated with a request for health-relatedinformation), etc. As will be appreciated, heightened levels of securityprovided may also be provided in certain circumstances as a result ofthe operation of other fraud prevention algorithms (e.g., a pattern ofrequests for financial information may be identified as being unusualand therefore potentially fraudulent).

As discussed above, the action required to be taken by the user in orderto approve such an information exchange may also be varied depending onthe circumstances. For example, in some instances, approval may bepassively granted based on the settings the user has set for their data(e.g., no affirmative action is required by the user to give the user'sspouse access to the user's data). In other instances, affirmativeaction may be required to be taken on the part of the user. Again, thetype of action may vary depending on the situation and the level ofsecurity to be provided. For example, in some instances, the approvalmay require the user to simply press a button labeled “approve” on theuser computing device 120. In other instances, the approval may requirethe user entering a pin number or other secret password or code on theuser computing device 120. As another example, biometric authentication,such as a body print, may be required. As will be appreciated, anynumber of different actions and different types of transactions may berequired of a user in order to provide different levels of security inthe context of particular information exchange transactions.

As will also be appreciated, in various embodiments, the informationwallet system 100 may provide greater security than physical paper formsbecause the information is fully encrypted when exchanged and people donot have direct visual access to confidential data. The adapters on theentity computing systems 105 may provide an additional layer ofprotection by enforcing security settings of the information walletcomputing system 115. In various embodiments, the information walletsystem 100 may also provide enhanced security by providing an easieralternative to manually managing large amounts of password andauthentication data. A user who is required to have a plurality ofusernames and passwords for different accounts may feel compelled tocatalog the plurality of passwords and associated websites on a hardcopy for easy access. For example, a user may write down a list ofpasswords and keep the passwords within reach for easy reference,thereby impairing the security of the sensitive information. In oneembodiment, after using the information wallet for over a period oftime, the user may no longer have to remember a plurality of passwordsfor a plurality of websites or entities, etc. The user mayself-authenticate using a combination of the identity of the device,biometric information acquired from the user by the user computingdevice 120, a single unified pin/password, or other identificationmethods.

In some embodiments, digital signatures may be used to certify theentity, the customer, the user, or the data. For example, driver'slicenses typically contain information such as the date of birth, name,address, eye color, height, weight, donor status, etc., of the holder ofthe driver's license. Assuming data for the driver's license is obtainedfrom an official government department, such as the department of motorvehicles for the state issuing the driver's license, the driver'slicense data may be digitally signed by the department of motor vehiclesusing standard certification technology. Hence, when this data iscommunicated to another entity computing system 105, the digitalsignature may be communicated with the data to certify that the data isaccurate. Additionally, biometric information received from governmentalauthorities may be used to certify an entity, the customer, the user, orthe data. For example, people are often required to submit to abackground check for certain employment, which often requires going to apolice station to obtain a set of fingerprints. The data collected atthe police station may be used for certification and self-authenticationpurposes.

FIG. 2 is a diagram showing various ways in which the information walletaccount (through an information wallet application 140) may be enrichedwith data. For example, data may be entered manually by the user via akeyboard or other suitable device. The user may enter informationincluding a name, address, phone number, contacts, calendar, and otherinformation. Also, image data may be received via a scanner, whereinscanned information may include, for example, a birth certificate,license, diploma, etc. Data may be received from smart devices such ascars, alarm clock, medical device, appliances, watches, phones, tablets,etc. and any application running on these devices. Biometric informationmay also be received, such as voiceprint, fingerprint, palm print,facial recognition information, etc. In some embodiments, the biometricinformation may be digitally signed either by a government agency, theentity that provides the cloud storage computing system 150 (e.g., abank), or other trusted authority. In such embodiments, the informationmay then be used for biometric authentication. The data received fromthe smart devices may be stored. The data may be stored in a database.The data may be stored in standard predefined fields of the database ormay be stored in customized fields as defined by the storing entity(e.g., in fields created by augmenting standard predefined fields). Thedata stored may be augmented with additional data or deleted. Storeddata may include metadata such as a time stamp or a version number. Datamay be permanently stored unless a delete command is received from theuser.

Data may be additionally received as an encrypted payload over email,USB drive, wired or wireless Internet, and so on. The encryption allowsthe information to be transferred safely without being accessed from anunauthorized party. The information wallet account may also receiveinformation from the context of a transaction with a merchant or entity.This may include purchase transaction information of any type, includingthe price of an item, the selection of a gift, additional warrantyinformation, receipt information, etc. The information walletapplication 140 may download data from online sources, such as onlineaccount information, telephone information, invoices, etc. The data fromthese and other sources may be used to enrich the information wallet andlater made accessible to the entity computing systems 105 via the usercomputing devices 120.

FIG. 3 is a schematic diagram showing how the data collected in FIG. 2can be published to various entities. As shown in FIG. 3 , a user mayshare information with government entities, merchants, healthcareproviders, employer, friends/family, and others. This information may beshared according to permissive authorizations and security levels asdiscussed above. FIG. 3 depicts the passive delivery of data wherein theuser has configured data to publish to entities automatically, so thatthe user does not need to remember to publish the data. For example, ifthe user has a change of address, the updated address may beautomatically transmitted to friends/family, employers, health careproviders, merchants, the government, financial institutions, and so on.While FIG. 3 shows automatic sending of data (e.g., publishing), as willbe appreciated, the information wallet system 100 may also be used forautomatically receiving data (e.g., subscribing). For example, the usermay subscribe to automatically receive data or messages regardingspecific content from a specific entity computing systems 105. Whilesome information may be configured to publish and subscribeautomatically, other information may be configured to blockautomatically. For instance, the system may be configured to preventpublishing information to specific entities (i.e. credit card companies)or to block automatic subscriptions to certain entity publications (i.e.weekly e-newsletters).

FIG. 4 is a schematic diagram showing tools provided to the user via auser information wallet application 140 operating on the user computingdevice 120 according to an exemplary embodiment. The tools shown in FIG.4 provide the user with different ways of entering, updating, accessingand analyzing their data stored in the cloud storage computing system150. As shown in FIG. 4 , by way of a top-level menu level of theinformation wallet application 140, the user may be provided with dataentry tools 401, view/search/report tools 402, entity interaction tools403, alert/offer/message queue tools 404, configure/administrate tools405, and other module tools 406. As shown in FIG. 4 , by selecting oneof the top-level menu items, the user may be taken to a drill down menuthat provides further options. In one embodiment, the data entry tools401 allow a user to enter information into the information wallet system100 through the user computing device 120. The data may be gathered bytyping information into a screen or by capturing the information viaother methods, including but not limited to capturing images, a vocalrecording, a video recording, etc. The data entry tool 401 may have adrill down menu that provides more functions for the application. In oneembodiment, the data entry tool 401 drill down menu includes modulessuch as customer key entry, customer scan/recognition, customer onlineconnect (attended) customer online connect (background), and encryptedpayload module. Customer key entry and scan/recognition modules supportthe data and information gathering functions discussed above. Thecustomer online connect modules, both attended and background,facilitate the functions of gathering the data and information from thecustomer and transferring the data and information to the cloud storagecomputing system 150. The encrypted payload module serves to encrypt thedata prior to transferring the data from the user computing device 120to the cloud storage computing system 150 of the information walletcomputing system 115. Any of the modules and functional units discussedabove or below may contain logic executable by a processor to achievethe described functions.

The view/search/report tool 402 may allow the customer or user to view,search, and retrieve information from the information wallet application140. For example, a customer may want to view specific information thatthe customer previously entered into the system through the data entrytool 401. To retrieve the information, the customer may use theview/search/report tool 402 module to enter certain parameters. Thebackend portion of the information wallet application 140 may retrievethe data from the cloud storage computing system 150 according to theparameters entered by the customer and deliver the information to theuser computing device 120. In one embodiment, the view/search/reporttool 402 drill down menu includes modules such as view by drill down,search, canned reports/graphs, ad hoc reports/graphs, and analysis.These modules allow functions described above to occur, such assearching for information using certain parameters. The view by drilldown menu may allow any information that the customer desires to view tobe displayed in a list, which further displays related information uponengaging the list. The modules also allow the information to bepresented in an organized, useful manner through avenues includinggraphs and reports. The information, data, reports, and graphs may beused for any type of analysis or metric functions. The analysis modulemay support functions such as retrieving a list of data, retrievingdetails behind the data, listing aspects of the data with accompanyingrelevant information, and so on. Analytics that may be performed mayinclude numerical calculations, metric evaluation, a summary or analysisof numeric data (such analysis including mean, average, standarddeviation, percentages, comparison, likelihood), cost projections, andso on. The user can also install applications (commonly called “apps”)that specifically provide reporting and/or analysis to the user based ondata in the informational wallet. For example, an application maycorrelate, driving habits, eating habits, and sleeping habits to healthdata (e.g., heart rate, blood pressure, oxygen saturation, etc.).

The entity transaction tool 403 allows the customer information walletto interact with an entity through the information wallet system 100. Inone embodiment, the entity transaction tool 403 drill down menu mayinclude modules such as entity initiated, customer initiated,repetitive/recurring, transaction templates, and complex/morphingtransactions. Through these modules, the customer may control how thecustomer interacts with the entity and how the entity is allowed tointeract with the customer through the information wallet system 100.The entity initiated module allows a customer to control how entitiesinitiate information requests or information transfers. The customerinitiated module allows a customer to determine the manner in which itinitiates transactions with an entity. For example, a customer mayconfigure the information wallet application to solicit coupons forsavings from specific entities. The repetitive/recurring module allowsthe customer to exact control on the interactions with the entitiesthrough the information wallet system 100 according to a specifiedperiod. For example, a customer may give recurring orders through therepetitive/recurring module (e.g. ordering medication every month). Thetransaction template module allows a customer to set a template on howinformation should be handled such that the transaction may easily occurin the future. Different entities may also have transaction templates,which could be transferred to the user computing device 120 and storedfor easy use. The complex/morphing transactions facilitate transactionsthat are more complex than straight-forward transactions and change overtime. These difficult transactions may involve greater manipulation andmonitoring, and the complex/morphing transactions modules helpfacilitated those functions. The user may be able to write rules thatgovern these complex transactions. For example, the user may specify arule that indicates that the user is to be prompted to order medicationif blood pressure went over a certain threshold within the month.

In one embodiment, the alert/offer/message queues tool 404 includes adrill down menu with modules including view alerts, view offers, andview messages. These modules assists in displaying alerts fromactivities, offers from entities, or messages from any computing systemconnected with the information wallet system. The displays, offers, ormessages may be new or historical. In one embodiment, theconfigure/administrate tool 405 contains a drill down menu with modulessuch as wallet security, offer configuration, publish/subscribeconfiguration, and alert configuration. The wallet security modulecontrols the security of the wallet. A customer may engage this moduleto edit the security settings of the wallet and of information sharedfrom the wallet. For example, the security level for certain informationmay be assigned using the wallet security module. The offerconfiguration module allows a customer to control which offers itreceives from entities. This module supports the function of blocking orallowing offers received by the information wallet. Thepublish/subscribe configuration controls the manner in which informationfrom the customer's information wallet account may be shared with otherentity computing systems 105. Any of the modules discussed throughoutthe disclosure may communicate or interact with other modules in orderto fulfill the required functions. For example, the publish/subscribeconfiguration module may interact with the wallet security module todetermine what information to publish and to which entity. In oneembodiment, the publish/subscribe configuration module determines theinformation's level of security as set in the wallet security module,then publishes the information according to the assigned security level.If information is set at a high level of security and requires a pin andthumbprint to publish, then the publish/subscribe configuration modulemay communicate with the wallet security module to enforce the pin andthumbprint requirement prior to publishing the information. The alertconfiguration modules allow a user to control when alerts may be givenby the system. For example, a user may use the alert configurationmodule to set up an alert each time a user's social security number issolicited or shared. Other module tools 406 represent a plurality ofmodules that may facilitate the implementation of any desired functionof the information wallet system.

FIG. 5 is a diagram showing information synchronization between variousinformation wallet (IW) adapters 505 and user applications. Variousadapters 505 may be developed to promote easy integration with businessapplications and systems, user devices, legacy systems, and so on. Theadapters 505 may be used to enforce common data protocols and schemas.The adapters 505 may also be used to synchronize information travelingbetween, for example, entity computing systems 105 and the informationwallet application 140 on a user computing device 120. As indicated inFIG. 5 , different adapters 505 may be developed for differentindustries and tailored to meet specific industry needs. Adapters 505may be developed for different software applications used by differenttypes of businesses. Different data schemas may be developed fordifferent domains (e.g., different industries). Again, the adapterswithin a common domain (e.g., healthcare) may use the same schemas topromote common data protocols and schemas. In various embodiments, theadapters may utilize both standard and non-standard schemas. Forexample, an entity may be permitted to add, change, and/or delete anydata element with the approval of the user. Those data elements can bestandard data elements within a domain or custom elements within adomain. In addition, an entity may be permitted to add a customextension to an existing data element that is either standard or custom.In all cases, the adds, changes, and/or deletes may be versioned andsaved such that the full data picture is preserved. In some situations,destructive deletes may be permitted with the approval of the user or atthe request of the user. Adapters 505 may also enforce securitystandards of the computing systems and information transferring betweenthe computing systems of the information wallet system 100.

FIG. 6 shows an information wallet system 600 according to an exemplaryembodiment. System 600 may utilize the above described systems andmethods associated with the information wallet system 100 to connectcomputing device 120 with second computing device 105, such as toexchange or transmit settings preferences and other information betweenuser computing device 120 and the second computing device 105. Thesecond computing device 105 may be included as part of the entities 105of system 100 shown in FIG. 1 . The second computing device 105 may beincluded as part of a second device and may be configured to control oneor more settings of the second device. For instance, system 600 may beused to automatically send a user's settings preferences to the secondcomputing device 105 upon a request of the user, such that one or moresettings of the second device may be modified to match the settingspreferences. The second device may include a vehicle of the user, a homeappliance, a media device, or another device having adjustable settingsand configured to receive user settings via system 600. According tosystem 600, user computing device 120, second computing device 105, andinformation wallet computing system 115 are connected and configured tocommunicate (e.g., transmit data) via network 170. The user computingdevice 120 includes information wallet application 140. The informationwallet application 140 may include computer software with executablecode and may be downloaded and installed on a device such as user device120. The information wallet application 140 may be configured to run onany operating system and may allow secure access to the informationwallet computing system 115.

According to the embodiment of FIG. 6 , the user computing device 120and the second computing device 105 are paired (e.g., connected,communicatively coupled, etc.), such that information may be transmittedfreely between the devices 120 and 105. The user computing device 120may be configured to pair with the second computing device 105 using theinformation wallet application 140 and the IW adapter 505. In oneembodiment, for instance, the user may pair the user computing device120 with the second computing device 105 by accessing the informationwallet application 140 stored on the device 120 and selecting an optionto pair the device 120 with the device 105. In another embodiment, thedevices 120 and 105 may be configured to automatically pair when thedevices 120 and 105 are within close proximity of each other (e.g.,within a specified distance of each other). For instance, the usercomputing device 120 may be configured to pair with the second device105 by near field communication (NFC) when the device 120 is placed inclose proximity to the device 105. The devices 120 and 105 may beconnected via the network 170, as shown in FIG. 6 , which may includeone or more of the Internet, a cellular network, near fieldcommunication (NFC), a Bluetooth connection, Wi-Fi, Wi-Max, aproprietary banking network, etc. In another embodiment, the devices 120and 105 may be paired using a wired connection.

The information wallet computing system 115 includes an informationwallet account 620. The information wallet account 620 may be an accountassigned to a user of the information wallet system 600 (e.g., a singleperson user, a family or other group, etc.). The information walletaccount 620 may be used to store information related to the user, suchas basic identifying information for the user, financial information,health information, or other information as may be determined by theuser. In one embodiment, the stored information (e.g., user information)includes settings preferences for one or more devices or systems thatmay be used by the user. For instance, the stored information mayinclude settings preferences for a vehicle, such as temperaturesettings, radio settings (e.g., preferred stations, volume settings,etc.), seat adjustment settings, mirror settings, airbag settings, lightsettings, and the like.

The information wallet account 620, including any data within, may beaccessed (e.g., entered, stored, edited, removed, etc.) by the user viathe information wallet application 140 of the user device 120. Theinformation wallet application 140 may include computer software withexecutable code and may be downloaded and installed on a device (e.g.,user device 120, second computing device 105, etc.). The informationwallet application 140 is configured to run on any operating system andallows secure access to the information wallet computing system 115.

According to system 600, the user device 120 communicates with thesecond computing device 105 via the network 170. The second computingdevice 105 may include an information wallet (IW) adapter 505 andadapter logic disposed within the IW adapter 505. For instance, the IWadapter 505 may be used to synchronize data between the second computingdevice 105 and the user device 120. The user device 120 may beconfigured to communicate with another computing system (e.g., system115), such as by communicating with an information wallet adapter 505included within the system. There may be a plurality of IW adaptersdisposed on a plurality of computing systems within the informationwallet system 600 and configured to act as secure portals in whichinformation is sent and received between the computing systems. Forinstance, the adapters 505 may be installed on the second computingdevice 105 to integrate the system 105 with the information walletcomputing system 115 (e.g., by configuring the adapter 505 to interactsecurely with an adapter of the system 115).

Information wallet adapters 505 may be configured to request and/or sendcertain types of information. Adapters 505 may also be configured toreceive requests for information, such as from one or more computingsystems or devices within the information wallet system 600. Theconfiguration may be written into executable code in the adapter logicand executed by a processor of the second computing device 105, forinstance. The IW adapters 505 may also contain adapter logic whichallows the second computing device 105 to connect with and operate withthe user computing device 120 and the information wallet computingsystem 115 through the information wallet system 600. The adapter logicmay also be executable by a processor and may allow the second computingdevice 105, for instance, to implement a number of functions. The IWadapter 505 on the second computing device 105 may allow a second deviceto integrate into or pair with the information wallet system 600 withouthaving to perform a full overhaul of the second computing device 105.The IW adapters 505 may also provide a compartmentalized method ofadapting the second computing device 105 to the information walletsystem 600, which may further allow greater ease in transitioning,implementing, and using the system 600. The IW adapters 505 may beconfigured to fully integrate with the second computing device software,information or financial accounts of the user, and other software. TheIW adapters 505 may also be configured to communicate between the cloudstorage computing system 150 and the information wallet system 600. Inone embodiment, the IW adapters 505 are configured to communicate withand perform functions such as synchronize information, integratetechnologies, and enforce the security procedures set by a user or acomputing system.

According to the system 600, the second computing device 105 isconfigured to receive information from the information wallet computingsystem 115 (e.g., the information wallet account 620). For instance,information stored on the information wallet account 620 (e.g., enteredand stored to the account 620 by the user) may be transmitted to thesecond computing device 105 via network 170. The second computing device105 is also configured to receive information from the user device 120via the network 170, such as by the user entering information using aninput device or interface of the user device 120 (e.g., using theinformation wallet application 140) and transmitting the information tothe second computing device 105. As described above, the user device 120and the second computing device 105 may be securely integrated orotherwise communicatively connected using an IW adapter 505. The IWadapter 505 may allow a user to interact with the second computingdevice 105 (e.g., using the information wallet application 140). Theuser may also access the information wallet account 620 in order tostore, edit, delete, and otherwise manipulate the information within theaccount 620 using the information wallet application 140.

The system 600 may also include a financial institution computing system610 held by a financial institution. In one embodiment, the financialinstitution computing system 610 is responsible for and houses theinformation wallet computing system 115. In this embodiment, theinformation wallet accounts held by the financial institution mayinclude accounts associated with persons not having a financial accountwith the financial institution. However, users having both financialaccounts and information wallet accounts held by the financialinstitution may be able to transfer information between the two types ofaccounts, or the two accounts may be integrated into a single account.The computing system 610 may include various storage (e.g., cloudstorage computing system 150, external entity storage system 160, etc.),such as banking servers, configured to store data relating to aplurality of customer accounts, financial records, and other documents.The stored data may be backed up in multiple data centers, for example,data centers that are geographically diverse. The computing system 610may include account management logic 615, which may include programmingmodules stored in a memory and configured to be executed by a processor(e.g., the processor of the banking server, etc.). The accountmanagement logic 615 may be part of the banking servers or may reside ona separate server within the computing system 610. The accountmanagement logic 615 may perform any typical functions and transactionsassociated with managing and maintaining a bank account for a customer,including, but not limited to opening new accounts, closing existingaccounts, crediting accounts, debiting accounts, transferring fundsbetween accounts, processing debit and credit card transactions,calculating and applying interest, calculating balances, performingaccount transfers, processing electronic bill payment transactions, andthe like. The account management logic 615 may include transactionprocessing logic 616 to perform the above recited tasks. The accountmanagement logic may be configured to manage a plurality of types ofaccounts, including but not limited to demand deposit accounts (e.g.,checking accounts, savings accounts, etc.), credit card accounts, linesof credit, and the like. The financial institution computing system 610may include interface logic (e.g., network logic) configured to connectthe financial institution computing system 610 to computing systemsassociated with the plurality of users (e.g., user computing devices120, second computing devices 105, etc.) by way of a communicationnetwork (e.g., network 170). The financial institution computing system610 may include import logic configured to import financial statementsregarding the financial accounts on a scheduled basis and/or to importuser-provided information or documents on a user-determined timingbasis.

The information wallet system 600 may be utilized to provideuser-related information (e.g., information related to a user of system600, system 100, information wallet account 620, etc.) that is relatedto or associated with the second device or the second computing device105. The second device may be a vehicle driven by or holding the user, ahome appliance utilized by the user (e.g., a washer or dryer, a stove, arefrigerator, etc.), a media device (e.g., a television, a stereo, agaming device, etc.), or another device having adjustable settings. Inresponse to receipt of the user information, the second computing device105 associated with the second device may automatically adjust thesettings based on the user information. For instance, the second devicemay be a rental car and the user may utilize the system 600 to send userinformation regarding vehicle preferences to the system 105 of therental car. The rental car computing system 105 may then adjust one ormore settings of the rental car according to settings preferences of theuser, such as by adjusting the seat, the mirrors, or the volume of thestereo. The settings preferences provided by the user may depend on aparticular device being utilized. The user computing device 120 may alsobe used as a remote for a television or other electronic device. Forinstance, the user computing device 120 may be “paired” or otherwiseconnected with a television (e.g., the second device) and automaticallyapply the user's preferences to the television. In this way, the usercomputing device 120 may “match” the user's favorite television programsor networks with the paired television to allow the user to control thetelevision to find a known program or network or otherwise changestations. The user's preferences may also include a volume level orother settings related to or associated with the television. Thetelevision may utilize the IW adapter 505 to retrieve customerpreferences or favorites and allow the user to select or find channelsfrom a known device (e.g., a home device) regardless of the interface ofthe paired television.

The information wallet computing system 115 is configured to receiveuser information associated with a user of the system 600, such assettings preferences related to the second device. Upon receipt, theinformation may be stored within the information wallet account 620. Theinformation wallet computing system 115 is configured to receive thesettings preferences from the user computing device 120. For instance,the user may manually access the information wallet account 620 via theinformation wallet application 140 stored on the user computing device120. The user may enter settings preferences via the application 140 tobe stored within the account 620 (e.g., received by the system 115directly from the user). The user may select a type of device (e.g.,passenger vehicle, stereo, video game device, etc.) or a device categoryor system (e.g., kitchen devices, hotel room, bathroom devices, etc.)and store settings preferences related to the device or system. The usercomputing device 120 may be configured to automatically send thesettings preferences to the information wallet computing system 115 uponreceipt from the user, or to send the settings preferences manually inresponse to an additional signal or input from the user (e.g., receivedvia the application 140).

The information wallet computing system 115 is also configured toreceive settings preferences via a paired device (e.g., second device105 paired with the user computing device 120). As described above andshown in FIG. 6 , the second computing device 105 and the user computingdevice 120 may be paired using the network 170. When the devices 120 and105 are paired, settings adjustments and preferences for the seconddevice 105 that are controlled using the second computing device 105 maybe sent to the information wallet computing system 115 and stored withinthe information wallet account 620. In one embodiment, the secondcomputing device 105 is configured to send the settings preferences tothe system 115 directly. For instance, the second computing device 105may be configured to include information regarding the paired usercomputing device 120 and/or the user so that the information walletcomputing system 115 is able to store the information within theappropriate information wallet account (e.g., account 620). The secondcomputing device 105 may also be configured to send the information tothe information wallet computing system 115 via the user computingdevice 120. For instance, the second computing device 105 may sendinformation, including settings preferences, to the user computingdevice 120, and the user computing device 120 may transmit theinformation to the information wallet computing system 115 (e.g., viathe information wallet application 140).

Similarly, the information wallet computing system 115 may also bepaired with an entity. For instance, data stored within the informationwallet computing system 115 may be automatically shared and updated withan entity associated with the user, such as a friend or a physician. Theuser may be able to select the data that is shared with one or moreentities using the information wallet application 140. The informationmay be sent and/or updated automatically or sent manually by the userusing the application 140. As an example, the user may sendhealth-related data to a physician by pairing the information walletcomputing system 115 with a system or account of the physician.

The settings preferences may be stored automatically. For instance, thesecond computing device 105 may be configured to send settingspreferences to the information wallet computing system 115 automaticallywhen a setting is adjusted (e.g., by the user), after a setting has beenadjusted but remains static for a period of time, upon scheduled timeintervals, when the device 105 is turned on or turned off, and so forth.The settings preferences may also be stored manually. For instance, thesecond computing device 105 may be configured to send settingspreferences to the information wallet computing system 115 upon requestby the user, such as using the information wallet application 140.

In another embodiment, the information wallet computing system 115 isconfigured to determine (e.g., calculate, estimate, etc.) one or moresettings preferences for the user. The information wallet computingsystem 115, using a processor of the system 115, may be configured toaccess the information wallet account 620 and determine one or moresettings preferences based on the information stored within the account620. For instance, the system 115 may determine seat settings and mirrorsettings for a vehicle based on a size of the person, including a heightor weight, which may be stored within the account 620 (e.g., driver'slicense, health records, etc.). As another example, the system 115 mayautomatically adjust any settings preferences based on an impairment ofthe user, such as a hearing or vision impairment (e.g., to use onlyvisual output for a user with a hearing impairment), as determined usinginformation within the account 620. The information wallet computingsystem 115 may also be configured to seek further input based on theinformation stored within the account 620 in order to determine thesettings preferences. The information wallet computing system 115 maydetermine the settings preferences based on the stored information andthe additional information received from the user. The system 115 may beconfigured to request information from the user via the informationwallet application 140. The information wallet computing system may alsobe configured to determine additional settings preferences based onsettings preferences manually entered by the user. The informationwallet computing system 115 may be configured to store any determinedsettings preferences within the information wallet account 620. Thesettings preferences that are determined by the information walletcomputing system 115 may be automatically stored or stored subject toapproval by the user (e.g., via the application 140).

The information wallet computing system 115 may be configured to storethe settings preferences according to a device type or function, such asto later apply appropriate settings preferences when using anothersimilar device. In one embodiment, the information wallet computingsystem 115 is configured to sort settings preferences or otherinformation received based on a device type, function, or based onanother characteristic suitable for the particular application of system600. For instance, when the user drives a paired vehicle, theinformation wallet computing system 115 may receive settings preferencesrelated to a driver seat or mirror position of the vehicle. Theinformation wallet computing system 115 may store these preferences foruse with another vehicle. The information wallet computing system 115may also receive settings preferences related to the stereo within thevehicle, such as station preferences or sound levels. The informationwallet computing system 115 may store these preferences for use withanother vehicle, as well, but may also be configured to store thesepreferences for use with a home stereo that serves a similar function.

The information wallet computing system 115 is configured to sendinformation stored within the information wallet account 620, includingsettings preferences related to the second device 105 and the user, tothe second computing device 105 using the system 600. For instance, theinformation wallet computing system 115 may send settings preferencesrelated to the device 105 when the user is utilizing the second device105, or when the user computing device 120 (or the information walletcomputing system 115) is paired with the second device 105. Theinformation wallet computing system 115 may be configured to send thesettings preferences directly to the second computing device 105, or theinformation wallet computing system 115 may deliver the settingspreferences to the user computing device 120 (e.g., through theinformation wallet application 140) in order for the device 120 to sendthe information to the second computing device 105.

In one embodiment, the information wallet computing system 115 isconfigured to send settings preferences to the second device 105 inresponse to a request (e.g., from the user via the user computing device120, from the second computing device 105). The user computing device120 and/or the second computing device 105 may be configured to send arequest for settings preferences to the information wallet computingsystem 115 when the second computing device 105 is paired with the usercomputing device 120, for instance. In another embodiment, theinformation wallet computing system 115 is configured to send settingspreferences to the second computing device 105 that are related to thesecond device 105 when the information wallet computing system 115 isconnected to the second computing device 105 (e.g., via the network170), such as when the second computing device 105 is paired with theuser computing device 120.

Referring now to FIG. 7 , a flow chart of a process 700 for pairing aninformation wallet account (e.g., account 620) with a computing device(e.g., second computing device 105) is shown according to an exampleembodiment. The process 700 may be performed using systems 100 or 600.For instance, the process 700 may be performed by an information walletcomputing system 115 configured to communicate (e.g., send and receiveinformation) with a user computing device 120 and a second computingdevice 105. In one embodiment, the process 700 may be implemented by aserver having a memory and a processor, such as a server stored withinthe information wallet computing system 115 and/or stored within thefinancial institution computing system 610. The processor of the servermay carry out the steps of process 700. The server may be controlled byone or more entities, such as a data storage entity (e.g., when serverresides within the information wallet computing system 115) or afinancial institution (e.g., when server resides within the financialinstitution computing system 610).

At 702, user information is received from the user computing device 120.The user information may be related to a user of the information walletaccount 620. The user information may include any of the informationdescribed above in relation to the information wallet, such as basicidentifying information for the user, physical characteristics (e.g.,height, weight, etc.), location information, and other information thatmay be useful for the purposes of systems 100, 600 and/or the process700. The user information may be entered manually by the user using theinformation wallet application 140 stored on the user computing device120. The user information may be stored on the information walletaccount 620. In one embodiment, the user information is provided by theuser in response to a request from the information wallet computingsystem 115 to provide specific user information. For instance, theinformation wallet computing system 115 may be configured to requestuser information in order to determine one or more settings preferencesfor the second computing device 105. The user information may also berelated to the second computing device 105. For instance, in oneembodiment, the second computing device 105 includes a vehicle. In thisembodiment, the user information may include seat position preferences,stereo-related preferences, or other vehicle-related preferences inorder to determine one or more settings preferences for the vehicle(i.e., second computing device 105). In this embodiment, the userinformation may also include data or information that may be used toestimate one or more settings preferences for the vehicle, such asphysical characteristics of the user in order to estimate a preferredseat or mirror position for the vehicle.

At 704, one or more user settings preferences are determined for thesecond computing device 105 based on the user information. In oneembodiment, the user information includes one or more user settingspreferences related to the second computing device 105 and theinformation wallet computing system 115 is configured to determine atleast some of the user settings preferences for the second computingdevice 105 by pulling the preferences from the user information. Theinformation wallet computing system 115 may also be configured todetermine one or more user settings preferences by estimating the usersettings preferences based on the user information, such as describedabove. The information wallet computing system 115 may send a requestfor additional information to the user computing device 120 in order toestimate the one or more user settings preferences. The user settingspreferences and the user information may be automatically stored withinthe information wallet account 620 (e.g., within the information walletcomputing system 115).

At 706, an information request is received to send information to thesecond computing device 105. The information request includes a requestto send user settings preferences to the second computing device 105.The request may be received from the user computing device 120 or thesecond computing device 105 (e.g., via the user computing device 120).The request may include a request for specific user settings preferencesand/or a request for any user settings preferences that are related tothe second computing device 105. For instance, if the second computingdevice 105 is a vehicle, the request may include a request for any usersettings preferences that are related to a vehicle or to driving.

At 708, user settings preferences are sent to the user computing device120 (e.g., by the information wallet computing system 115). The usersettings preferences may be viewed by the user on the user computingdevice 120 using the information wallet application 140. The usersettings preferences sent to the user may be only those related to theconnected second computing device 105. At 710, feedback is received fromthe user computing device 120 (e.g., the user). The feedback may berelated to the user settings preferences. For instance, the user may beable to modify the user settings preferences received using theinformation wallet application 140. The user may be able to delete oneor more user settings preferences, edit the preferences, or addadditional preferences related to the second computing device 105. Inone embodiment, a request for additional information may be sent to theuser computing device 120 along with the user settings preferences, andthe feedback may include responses to the requests.

At 712, the user settings preferences are adjusted (e.g., by theinformation wallet computing system 115) based on the feedback providedby the user. For instance, the feedback may include manual adjustmentsmade to one or more of the user settings preferences, and the system 115may be configured to adjust the user settings preferences accordinglyand store the updated user settings preferences within the informationwallet account 620. The feedback may also include additional userinformation, such as information provided in response to a request sentby the information wallet computing system 115. The system 115 mayadjust the user settings preferences according to this additional userinformation, as well, or the system 115 may generate or determineadditional user settings preferences based on the feedback.

At 714, confirmation of the user settings preferences is received fromthe user computing device 120. The confirmation may be receivedsimultaneously with the feedback from the user computing device 120, inone embodiment. The user of the user computing device 120 may provide aconfirmation using the information wallet application 140 if the useragrees with or accepts the user settings preferences provided by theinformation wallet computing system 115.

At 716, the confirmed user settings preferences are sent to the secondcomputing device 105. The user settings preferences may be related tothe second computing device 105. The user settings preferences areuseable by the second computing device 105 to set or adjust one or moresettings of the second computing device 105. For instance, in anembodiment in which the second computing device 105 is a vehicle, theuser settings preferences may include instructions or guidelines forautomatically adjusting a seat position, a mirror position, stereosettings, including a volume level, or other adjustable settings withina vehicle. If any of the settings are automatically adjustable, such asbeing controlled by the second computing device 105, the secondcomputing device 105 may automatically adjust the settings. The usersettings preferences may also be sent simultaneously to the usercomputing device 120 and made viewable to the user. The user may viewthe settings preferences in order to manually adjust one or moresettings of the vehicle (or another computing device 105).

At 718, additional user information is received from the secondcomputing device 105. The second computing device 105 may be paired withthe information wallet computing system 115 when the user computingdevice 120 is connected to the second computing device 105, such thatthe second computing device 105 is configured to transmit information ordata to the information wallet computing system 115. The secondcomputing device 105 and the information wallet computing system 115 maybe paired by connecting the user computing device 120 with the secondcomputing device 105 using the network 170, such as by a Bluetooth orNFC connection (or other types of network connections, as describedabove). The second computing device 105 may be configured to sendadditional user information to the information wallet computing system115 based on adjustments to settings of the second computing device 105that are made by the user when the second computing device 105 and theinformation wallet computing system 115 are paired. The second computingdevice 105 may also be configured to send updated user information, suchas settings adjustments made by the user, without pairing the secondcomputing device 105 with the system 115. For instance, the secondcomputing device 105 may send information to the user computing device120 and the information may be relayed manually to the informationwallet computing system 115 (e.g., by the user).

At 720, the user settings preferences are updated based on theadditional user information received from the second computing device105. For instance, the user settings preferences may be updated to matchthe setting used by the user the last time the second computing device105 was used or the last time the second computing device 105 was pairedwith the information wallet computing system 115.

The embodiments of the present invention have been described withreference to drawings. The drawings illustrate certain details ofspecific embodiments that implement the systems and methods and programsof the present invention. However, describing the invention withdrawings should not be construed as imposing on the invention anylimitations that may be present in the drawings. The present inventioncontemplates methods, systems and program products on anymachine-readable media for accomplishing its operations. The embodimentsof the present invention may be implemented using an existing computerprocessor, or by a special purpose computer processor incorporated forthis or another purpose or by a hardwired system.

As noted above, embodiments within the scope of the present inventioninclude program products comprising machine-readable media for carryingor having machine-executable instructions or data structures storedthereon. Such machine-readable media can be any available media that canbe accessed by a general purpose or special purpose computer or othermachine with a processor. By way of example, such machine-readable mediacan comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical diskstorage, magnetic disk storage or other magnetic storage devices, or anyother medium which can be used to carry or store desired program code inthe form of machine-executable instructions or data structures and whichcan be accessed by a general purpose or special purpose computer orother machine with a processor. Combinations of the above are alsoincluded within the scope of machine-readable media. Machine-executableinstructions comprise, for example, instructions and data which cause ageneral purpose computer, special purpose computer, or special purposeprocessing machines to perform a certain function or group of functions.

Embodiments of the present invention have been described in the generalcontext of method steps which may be implemented in one embodiment by aprogram product including machine-executable instructions, such asprogram code, for example in the form of program modules executed bymachines in networked environments. Generally, program modules includeroutines, programs, objects, components, data structures, etc. thatperform particular tasks or implement particular abstract data types.Machine-executable instructions, associated data structures, and programmodules represent examples of program code for executing steps of themethods disclosed herein. The particular sequence of such executableinstructions or associated data structures represent examples ofcorresponding acts for implementing the functions described in suchsteps.

As previously indicated, embodiments of the present invention may bepracticed in a networked environment using logical connections to one ormore remote computers having processors. Those skilled in the art willappreciate that such network computing environments may encompass manytypes of computers, including personal computers, hand-held devices,multi-processor systems, microprocessor-based or programmable consumerelectronics, network PCs, minicomputers, mainframe computers, and so on.Embodiments of the invention may also be practiced in distributedcomputing environments where tasks are performed by local and remoteprocessing devices that are linked (either by hardwired links, wirelesslinks, or by a combination of hardwired or wireless links) through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote memory storage devices.

An exemplary system for implementing the overall system or portions ofthe invention might include a general purpose computing computers in theform of computers, including a processing unit, a system memory, and asystem bus that couples various system components including the systemmemory to the processing unit. The system memory may include read onlymemory (ROM) and random access memory (RAM). The computer may alsoinclude a magnetic hard disk drive for reading from and writing to amagnetic hard disk, a magnetic disk drive for reading from or writing toa removable magnetic disk, and an optical disk drive for reading from orwriting to a removable optical disk such as a CD ROM or other opticalmedia. The drives and their associated machine-readable media providenonvolatile storage of machine-executable instructions, data structures,program modules and other data for the computer. It should also be notedthat the word “terminal” as used herein is intended to encompasscomputer input and output devices. Input devices, as described herein,include a keyboard, a keypad, a mouse, joystick or other input devicesperforming a similar function. The output devices, as described herein,include a computer monitor, printer, facsimile machine, or other outputdevices performing a similar function.

It should be noted that although the diagrams herein may show a specificorder and composition of method steps, it is understood that the orderof these steps may differ from what is depicted. For example, two ormore steps may be performed concurrently or with partial concurrence.Also, some method steps that are performed as discrete steps may becombined, steps being performed as a combined step may be separated intodiscrete steps, the sequence of certain processes may be reversed orotherwise varied, and the nature or number of discrete processes may bealtered or varied. The order or sequence of any element or apparatus maybe varied or substituted according to alternative embodiments.Accordingly, all such modifications are intended to be included withinthe scope of the present invention. Such variations will depend on thesoftware and hardware systems chosen and on designer choice. It isunderstood that all such variations are within the scope of theinvention. Likewise, software and web implementations of the presentinvention could be accomplished with standard programming techniqueswith rule based logic and other logic to accomplish the various databasesearching steps, correlation steps, comparison steps and decision steps.

The foregoing description of embodiments of the invention has beenpresented for purposes of illustration and description. It is notintended to be exhaustive or to limit the invention to the precise formdisclosed, and modifications and variations are possible in light of theabove teachings or may be acquired from practice of the invention. Theembodiments were chosen and described in order to explain the principalsof the invention and its practical application to enable one skilled inthe art to utilize the invention in various embodiments and with variousmodifications as are suited to the particular use contemplated. Othersubstitutions, modifications, changes and omissions may be made in thedesign, operating conditions and arrangement of the embodiments withoutdeparting from the scope of the present invention.

What is claimed is:
 1. An information wallet computing system, comprising: an information wallet account associated with a user of the system; and a server having a memory and a processor, wherein the processor is configured to: receive user information from a user computing device remote from the server, wherein the user information is related to the user of the information wallet account; determine, based on at least a physical characteristic in the user information, one or more user settings preferences related to a second computing device having an information wallet adaptor configured to enforce a common data protocol and to synchronize information traveling between the user computing device and the information wallet computing system, the second computing device having one or more adjustable settings relating to a physical configuration of the second computing device, the second computing device being remote from the server; receive, from the user computing device, an information request transmitted by the user computing device to the server responsive to the user computing device being paired with the second computing device, wherein the information request includes a request to send the one or more user settings preferences to the second computing device, the request identifying the second computing device; send, responsive to the user computing device being paired with the second computing device, the one or more user settings preferences to the second computing device, to cause the second computing device to adjust one or more settings of the second computing device based on the one or more user settings preferences; receive additional user information from the second computing device, wherein the additional user information is related to use of the second computing device by the user; and update the one or more user settings preferences based on the additional user information.
 2. The system of claim 1, wherein the information wallet computing system resides in a financial institution computing system, and further comprising account management logic stored on the machine readable storage media and configured to manage accounts respectively associated with a plurality of users, the accounts including bank accounts and information wallet accounts.
 3. The system of claim 1, wherein at least one of the one or more user settings preferences is determined by estimating the at least one user settings preference based on the user information.
 4. The system of claim 1, further comprising an information wallet application stored on the user computing device and configured to provide an interface between the user computing device and the information wallet computing system.
 5. The system of claim 1, wherein the memory includes a cloud storage computing system and the information wallet computing system is stored on the cloud storage computing system.
 6. The system of claim 1, wherein the processor is further configured to, prior to sending the one or more user settings preferences to the second computing device: send the one or more user settings preferences to the user computing device; and receive a confirmation of the one or more user settings preferences from the user computing device.
 7. The system of claim 6, wherein the processor is further configured to: receive feedback related to the one or more user settings preferences from the user computing device prior to receiving the confirmation from the user computing device; and adjust the one or more user settings preferences based on the feedback.
 8. The system of claim 1, wherein the processor is further configured to: send the updated user settings preferences to the second computing device, wherein the updated user settings preferences are useable by the second computing device to adjust one or more settings of the second computing device.
 9. The system of claim 1, wherein the user information received from the user computing device includes information relating to at least one physical characteristic of the user.
 10. The system of claim 1, wherein the second computing device comprises one of a vehicle of the user and a home appliance of the user.
 11. The system of claim 10, wherein the one or more user settings preference of the second computing device comprise at least one of a temperature setting, a radio setting, a seat adjustment setting, a mirror setting, an airbag setting, and a light setting.
 12. A method for pairing an information wallet account with a second computing device having an information wallet adaptor configured to enforce a common data protocol and to synchronize information traveling between a user computing device and the information wallet computing system, the second computing device having one or more adjustable settings relating to a physical configuration of the second computing device, the method being implemented by a server residing in a financial institution computing system and having a memory and a processor, the method comprising: receiving user information from the user computing device remote from the server, wherein the user information is related to a user of the information wallet account; determining, based on at least a physical characteristic in the user information, one or more user settings preferences, wherein the one or more user settings preferences are related to the second computing device, the second computing device being remote from the server; receiving, from the user computing device, an information request transmitted by the user computing device to the server responsive to the user computing device being paired with the second computing device, wherein the information request includes a request to send the one or more user settings preferences to the second computing device, the request identifying the second computing device; sending, responsive to the user computing device being paired with the second computing device, the one or more user settings preferences to the second computing device, to cause the second computing device to adjust one or more settings of the second computing device based on the one or more user settings preferences; receiving additional user information from the second computing device, wherein the additional user information is related to use of the second computing device by the user; and updating the one or more user settings preferences based on the additional user information.
 13. The method of claim 12, further comprising: managing accounts stored in the financial institution computing system and respectively associated with a plurality of users, the accounts including bank accounts and information wallet accounts.
 14. The method of claim 12, wherein the user information is received from the user computing device via an information wallet application stored on the user computing device.
 15. The method of claim 12, wherein the financial institution computing system includes a cloud storage computing system and the information wallet account is stored within the cloud storage computing system.
 16. The method of claim 12, wherein at least one of the one or more user settings preferences is determined by estimating the at least one user settings preference based on the user information.
 17. The method of claim 12, further comprising, prior to sending the one or more user settings preferences to the second computing device: sending the one or more user settings preferences to the user computing device; and receiving a confirmation of the one or more user settings preferences from the user computing device.
 18. The method of claim 17, further comprising: receiving feedback related to the one or more user settings preferences from the user computing device prior to receiving the confirmation from the user computing device; and adjusting the one or more user settings preferences based on the feedback.
 19. The method of claim 12, further comprising: sending the updated user settings preferences to the second computing device, wherein the updated user settings preferences are useable by the second computing device to adjust one or more settings of the second computing device.
 20. The method of claim 12, wherein the user information received from the user computing device includes information relating to at least one physical characteristic of the user. 